Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Creating a new session type

Because session types are designed to inherit settings from other session types, the preferred method for creating new session types is to extend an existing session type. When you create a new session type in this way, you only have to specify the new items or changed values rather than everything that the session needs to run.

As an example, you will create a session type for the DynSports sample application by extending the Default session type.

To create a new session type:

From the Administration window, choose Session Session Type Control.

The Session Type Maintenance window appears, as shown:



Note the hierarchy of the session types. The standard development session (ICFDev) inherits from DynDevelopment, which inherits from DynCS, which inherits from DynDBBound, which inherits from Dynamics, which inherits from the Basic session type.

Right-click on the Basic Dynamics DynDBBound DynCS Default node, and choose the Add Session Type pop-up option. The Session Type Maintenance window appears in the right frame, as shown:



Type DynSports as the Session type code value.
Type DynSports sample application session in the Session type description field.
Clear the Automatic reconnect toggle box, if necessary. You set this option when you want the framework to automatically attempt to reconnect a dropped AppServer connection and restore the session context.
Select the WIN32 option in the Valid operating systems choices.
Choose Never for the Inactivity timeout options. The session will keep running until the user actively shuts it down.
Leave the physical session type selections as they are. You do not need to add any for this session type.
Choose Save. The new session type appears under the Default node, as shown:

Defining managers for a session type

Now that you have a new session type, you must modify it to suit your needs. Under each session type, there are three nodes that enable you to configure the session. The first node is the Required Managers node. If your new session type requires a manager that is not defined in one of the session types from which it inherits, you must add it through the Required Managers node.

Figure 2–2 shows the managers that the example session type, DynSports, inherits.

Figure 2–2: Required Manager inheritance

Suppose you want to turn the DynSports session type into a development session. You must add the Repository Design Manager to it.

To define a manager for a session type:

Expand the DynSports session type node.
Right-click on the Required Managers node, then choose the Add Required Manager pop-up option. The Required Manager Maintenance window appears in the right frame, as shown:



Select Repository Design Manager from the Manager type list.
Type 11 for the Startup order value. This is the order in which the Connection Manager starts the necessary managers.
Unselect the System owned toggle box, if necessary. You set this option when the manager can only be modified by users with appropriate privileges.
Choose Save.

For more information on Progress Dynamics managers, see the "Defining managers" section.

Defining properties for a session type

The second node that enables you to configure a session type is the Session properties node. If your new session type requires properties that are not defined in one of the session types from which it inherits, you must add it through the Session properties node. You might also want to override the value of an inherited property. You do this by adding the property to the new session type and assigning it a new value.

Figure 2–3 shows the session properties that the example session type, DynSports, inherits.

Figure 2–3: Session property inheritance

Continue with the example of turning the DynSports session type into a development session. There are several session properties that are set for development sessions. You can look at the session properties for the DynDevelopment session type to see them all. You will set one of them for DynSports.

To define session properties for a session type:

Expand the DynSports session type node.
Right-click on Session Properties, then choose the Add Session Property pop-up option. The Session Property Maintenance window appears in the right frame, as shown:



Choose the Lookup button for Property name. The Lookup Session Properties window appears, as shown:



Scroll to and double-click IDEPalette in the Session property name column.
Type PaletteDynamics for the Property value.
Choose Save.

For more information on Progress Dynamics session properties, see the "Creating session properties" section.

Defining services for a session type

The third node that enables you to configure a session type is the Session services node. If your new session type requires a session service that is not defined in one of the session types from which it inherits, you must add it through the Session properties node. You might also want to override the value of an inherited service. You do this by adding the service to the new session type and assigning it a new value.

Figure 2–4 shows the session services that the example session type, DynSports, inherits.

Figure 2–4: Session services inheritance

As shown in Figure 2–4, the DynSports session type inherits only two services, the default AppServer partition (ICFDevAS) and a network Repository connection (ICFDBn). To run the sample application, the DynSports session type needs a connection to the DynSports database. You can create that connection using the logical and physical services that you created in the "Creating a logical service" section and the "Creating a physical service" section.

To define session services for a session type:

Expand the DynSports session type node.
Right-click the Session Services node, then choose the Add Session Service pop-up option. The Session Service Maintenance window appears in the right frame, as shown:



Choose the Lookup button for Physical service code. The Lookup Physical Services dialog box appears, as shown:



In the Physical service code column, double-click dynsports.
Choose the Lookup button for Logical service code. The Lookup Logical Services window appears, as shown:



In the Logical service code column, double-click dynsports.
Choose Save.

For more information on Progress Dynamics services, see the "Defining session services" section.